Method and apparatus for point cloud coding

ABSTRACT

In some examples, an apparatus for point cloud compression/decompression includes processing circuitry. The processing circuitry determines a flag that indicates an enable/disable control for saving coding state in a largest coding unit (LCU) based coding of a point cloud. In some examples, the processing circuitry stores coding state information before a coding of a first LCU; and in response to the flag indicating an enable control, the processing circuitry restores, a coding state according to the stored coding state information before a coding of a second LCU. In some examples, in response to the flag indicating an enable control, the processing circuitry stores the coding state information before the coding of the first LCU. In some examples, in response to the flag indicating a disable control, the processing circuitry skip the storing/restoring of the coding state information.

INCORPORATION BY REFERENCE

This present application claims the benefit of priority to U.S. Provisional Application No. 63/139,161, “Additional Information on Node-Based Geometry and Attribute Coding for a Point Cloud” filed on Jan. 19, 2021, which is incorporated by reference herein in its entirety.

TECHNICAL FIELD

The present disclosure describes embodiments generally related to point cloud coding.

BACKGROUND

The background description provided herein is for the purpose of generally presenting the context of the disclosure. Work of the presently named inventors, to the extent the work is described in this background section, as well as aspects of the description that may not otherwise qualify as prior art at the time of filing, are neither expressly nor impliedly admitted as prior art against the present disclosure.

Various technologies are developed to capture and represent the world, such as objects in the world, environments in the world, and the like in 3-dimensional (3D) space. 3D representations of the world can enable more immersive forms of interaction and communication. Point clouds can be used as a 3D representation of the world. A point cloud is a set of points in a 3D space, each with associated attributes, e.g. color, material properties, texture information, intensity attributes, reflectivity attributes, motion related attributes, modality attributes, and various other attributes. Such point clouds may include large amounts of data and may be costly and time-consuming to store and transmit.

SUMMARY

Aspects of the disclosure provide methods and apparatuses for point cloud compression and decompression. In some examples, an apparatus for point cloud compression/decompression includes processing circuitry. The processing circuitry determines a flag that indicates an enable/disable control for saving coding state in a largest coding unit (LCU) based coding of a point cloud. In some examples, the processing circuitry stores coding state information before a coding of a first LCU; and in response to the flag indicating an enable control, restores, a coding state according to the stored coding state information before a coding of a second LCU. In some examples, in response to the flag indicating an enable control, the processing circuitry stores the coding state information before the coding of the first LCU. In some examples, in response to the flag indicating a disable control, the processing circuitry skipped the storing and/or the restoring of the coding state information.

In some embodiments, the processing circuitry decodes the flag from at least one of a sequence parameter set in a sequence header, a geometry parameter set in a geometry header, and a slice header.

In an embodiment, the processing circuitry decodes the flag from a geometry parameter set in a geometry header. Then, the processing circuitry stores, the coding state information before a geometry coding of the first LCU, and restores, the coding state according to the stored coding state information before a geometry coding of the second LCU.

In another embodiment, the processing circuitry decodes the flag from a sequence parameter set in a sequence header. Then, the processing circuitry stores, the coding state information before a geometry and attribute coding of the first LCU, and restores, the coding state according to the stored coding state information before a geometry and attribute coding of the second LCU.

In some embodiments, the processing circuitry starts the coding of the second LCU without a completion of the coding of the first LCU.

In some examples, the processing circuitry skips the restoring of the coding state according to the stored coding state information before the coding of the second LCU in response to the flag indicating a disable control for saving coding state.

In some examples, the processing circuitry skips the storing of the coding state information in response to the flag indicating the disable control for saving coding state.

In some examples, the coding state information includes at least one of context information and history geometry occupancy information.

Aspects of the disclosure also provide a non-transitory computer-readable medium storing instructions which when executed by a computer for point cloud encoding/decoding cause the computer to perform any one or a combination of the methods for point cloud encoding/decoding.

BRIEF DESCRIPTION OF THE DRAWINGS

Further features, the nature, and various advantages of the disclosed subject matter will be more apparent from the following detailed description and the accompanying drawings in which:

FIG. 1 is a schematic illustration of a simplified block diagram of a communication system in accordance with an embodiment;

FIG. 2 is a schematic illustration of a simplified block diagram of a streaming system in accordance with an embodiment;

FIG. 3 shows a block diagram of an encoder for encoding point cloud frames, according to some embodiments;

FIG. 4 shows a block diagram of a decoder for decoding a compressed bitstream corresponding to point cloud frames according to some embodiments;

FIG. 5 is a schematic illustration of a simplified block diagram of a video decoder in accordance with an embodiment;

FIG. 6 is a schematic illustration of a simplified block diagram of a video encoder in accordance with an embodiment;

FIG. 7 shows a block diagram of an encoder for encoding point cloud frames, according to some embodiments;

FIG. 8 shows a block diagram of a decoder for decoding a compressed bitstream corresponding to point cloud frames according to some embodiments;

FIG. 9 shows a diagram illustrating a partition of a cube based on the octree partition technique according to some embodiments of the disclosure.

FIG. 10 shows an example of an octree partition and an octree structure corresponding to the octree partition according to some embodiments of the disclosure.

FIG. 11 shows three quadtree partition examples.

FIG. 12 shows three binary tree partition examples.

FIG. 13 shows a diagram of an octree structure illustrating breadth first coding order.

FIG. 14 shows a diagram of an octree structure illustrating depth first coding order.

FIG. 15 shows a predictive tree example.

FIG. 16 shows a diagram of using a direct/forward transform architecture in the lifting based attribute coding at an encoder side.

FIG. 17 shows a diagram of using an inverse transform architecture in the lifting based attribute coding at a decoder side.

FIG. 18 shows a diagram of a region adaptive hierarchical transform (RAHT) forward transform architecture and a diagram of a RAHT inverse transform architecture.

FIG. 19 shows a tree structure corresponding to a point cloud according to some examples of the disclosure.

FIG. 20 shows a flow chart outlining a coding process for coding geometry information and/or attribute information in some examples.

FIG. 21 shows a flow chart outlining another coding process for coding geometry information and/or attribute information in some examples.

FIGS. 22A-22B show syntax table examples according to some embodiments of the disclosure.

FIG. 23 shows a flow chart outlining a coding process for coding geometry information and/or attribute information according to some embodiments of the disclosure.

FIG. 24 shows a flow chart outlining another coding process for coding geometry information and/or attribute information according to some embodiments of the disclosure.

FIG. 25 shows a flow chart outlining a process example in accordance with some embodiments.

FIG. 26 is a schematic illustration of a computer system in accordance with an embodiment.

DETAILED DESCRIPTION OF EMBODIMENTS

Aspects of the disclosure provide point cloud coding (PCC) techniques. PCC can be performed according to various schemes, such as a geometry-based scheme that is referred to as G-PCC, a video coding based scheme that is referred to as V-PCC, and the like. According to some aspects of the disclosure, the G-PCC encodes the 3D geometry directly and is a purely geometry-based approach without much to share with video coding, and the V-PCC is heavily based on video coding. For example, V-PCC can map a point of the 3D cloud to a pixel of a 2D grid (an image). The V-PCC scheme can utilize generic video codecs for point cloud compression. Moving picture experts group (MPEG) is working on G-PCC standard and V-PCC standard that respectively using the G-PCC scheme and the V-PCC scheme.

Point Clouds can be widely used in many applications. For example, point clouds can be used in autonomous driving vehicles for object detection and localization; point clouds can be used in geographic information systems (GIS) for mapping, and can be used in cultural heritage to visualize and archive cultural heritage objects and collections, etc.

Hereinafter, a point cloud generally may refer to a set of points in a 3D space, each with associated attributes, e.g. color, material properties, texture information, intensity attributes, reflectivity attributes, motion related attributes, modality attributes, and various other attributes. Point clouds can be used to reconstruct an object or a scene as a composition of such points. The points can be captured using multiple cameras, depth sensors or Lidar in various setups and may be made up of thousands up to billions of points in order to realistically represent reconstructed scenes or objects. A patch generally may refer to a contiguous subset of the surface described by the point cloud. In an example, a patch includes points with surface normal vectors that deviate from one another less than a threshold amount.

Compression technologies can reduce the amount of data required to represent a point cloud for faster transmission or reduction of storage. As such, technologies are needed for lossy compression of point clouds for use in real-time communications and six Degrees of Freedom (6 DoF) virtual reality. In addition, technology is sought for lossless point cloud compression in the context of dynamic mapping for autonomous driving and cultural heritage applications, and the like.

According to an aspect of the disclosure, the main philosophy behind V-PCC is to leverage existing video codecs to compress the geometry, occupancy, and texture of a dynamic point cloud as three separate video sequences. The extra metadata needed to interpret the three video sequences are compressed separately. A small portion of the overall bitstream is the metadata, which could be encoded/decoded efficiently using software implementation. The bulk of the information is handled by the video codec.

FIG. 1 illustrates a simplified block diagram of a communication system (100) according to an embodiment of the present disclosure. The communication system (100) includes a plurality of terminal devices that can communicate with each other, via, for example, a network (150). For example, the communication system (100) includes a pair of terminal devices (110) and (120) interconnected via the network (150). In the FIG. 1 example, the first pair of terminal devices (110) and (120) may perform unidirectional transmission of point cloud data. For example, the terminal device (110) may compress a point cloud (e.g., points representing a structure) that is captured by a sensor (105) connected with the terminal device (110). The compressed point cloud can be transmitted, for example in the form of a bitstream, to the other terminal device (120) via the network (150). The terminal device (120) may receive the compressed point cloud from the network (150), decompress the bitstream to reconstruct the point cloud, and suitably display the reconstructed point cloud. Unidirectional data transmission may be common in media serving applications and the like.

In the FIG. 1 example, the terminal devices (110) and (120) may be illustrated as servers, and personal computers, but the principles of the present disclosure may be not so limited. Embodiments of the present disclosure find application with laptop computers, tablet computers, smart phones, gaming terminals, media players, and/or dedicated three-dimensional (3D) equipment. The network (150) represents any number of networks that transmit compressed point cloud between the terminal devices (110) and (120). The network (150) can include for example wireline (wired) and/or wireless communication networks. The network (150) may exchange data in circuit-switched and/or packet-switched channels. Representative networks include telecommunications networks, local area networks, wide area networks, and/or the Internet. For the purposes of the present discussion, the architecture and topology of the network (150) may be immaterial to the operation of the present disclosure unless explained herein below.

FIG. 2 illustrates a simplified block diagram of a streaming system (200) in accordance with an embodiment. The FIG. 2 example is an application for the disclosed subject matter for a point cloud. The disclosed subject matter can be equally applicable to other point cloud enabled applications, such as, 3D telepresence application, virtual reality application, and the like.

The streaming system (200) may include a capture subsystem (213). The capture subsystem (213) can include a point cloud source (201), for example light detection and ranging (LIDAR) systems, 3D cameras, 3D scanners, a graphics generation component that generates the uncompressed point cloud in software, and the like that generates for example point clouds (202) that are uncompressed. In an example, the point clouds (202) include points that are captured by the 3D cameras. The point clouds (202), depicted as a bold line to emphasize a high data volume when compared to compressed point clouds (204) (a bitstream of compressed point clouds). The compressed point clouds (204) can be generated by an electronic device (220) that includes an encoder (203) coupled to the point cloud source (201). The encoder (203) can include hardware, software, or a combination thereof to enable or implement aspects of the disclosed subject matter as described in more detail below. The compressed point clouds (204) (or bitstream of compressed point clouds (204)), depicted as a thin line to emphasize the lower data volume when compared to the stream of point clouds (202), can be stored on a streaming server (205) for future use. One or more streaming client subsystems, such as client subsystems (206) and (208) in FIG. 2 can access the streaming server (205) to retrieve copies (207) and (209) of the compressed point cloud (204). A client subsystem (206) can include a decoder (210), for example, in an electronic device (230). The decoder (210) decodes the incoming copy (207) of the compressed point clouds and creates an outgoing stream of reconstructed point clouds (211) that can be rendered on a rendering device (212).

It is noted that the electronic devices (220) and (230) can include other components (not shown). For example, the electronic device (220) can include a decoder (not shown) and the electronic device (230) can include an encoder (not shown) as well.

In some streaming systems, the compressed point clouds (204), (207), and (209) (e.g., bitstreams of compressed point clouds) can be compressed according to certain standards. In some examples, video coding standards are used in the compression of point clouds. Examples of those standards include, High Efficiency Video Coding (HEVC), Versatile Video Coding (VVC), and the like.

FIG. 3 shows a block diagram of a V-PCC encoder (300) for encoding point cloud frames, according to some embodiments. In some embodiments, the V-PCC encoder (300) can be used in the communication system (100) and streaming system (200). For example, the encoder (203) can be configured and operate in a similar manner as the V-PCC encoder (300).

The V-PCC encoder (300) receives point cloud frames as uncompressed inputs and generates bitstream corresponding to compressed point cloud frames. In some embodiments, the V-PCC encoder (300) may receive the point cloud frames from a point cloud source, such as the point cloud source (201) and the like.

In the FIG. 3 example, the V-PCC encoder (300) includes a patch generation module (306), a patch packing module (308), a geometry image generation module (310), a texture image generation module (312), a patch info module (304), an occupancy map module (314), a smoothing module (336), image padding modules (316) and (318), a group dilation module (320), video compression modules (322), (323) and (332), an auxiliary patch info compression module (338), an entropy compression module (334), and a multiplexer (324).

According to an aspect of the disclosure, the V-PCC encoder (300), converts 3D point cloud frames into an image-based representation along with some meta data (e.g., occupancy map and patch info) that is used to convert the compressed point cloud back into a decompressed point cloud. In some examples, the V-PCC encoder (300) can convert 3D point cloud frames into geometry images, texture images and occupancy maps, and then use video coding techniques to encode the geometry images, texture images and occupancy maps into a bitstream. Generally, a geometry image is a 2D image with pixels filled with geometry values associated with points projected to the pixels, and a pixel filled with a geometry value can be referred to as a geometry sample. A texture image is a 2D image with pixels filled with texture values associated with points projected to the pixels, and a pixel filled with a texture value can be referred to as a texture sample. An occupancy map is a 2D image with pixels filled with values that indicate occupied or unoccupied by patches.

The patch generation module (306) segments a point cloud into a set of patches (e.g., a patch is defined as a contiguous subset of the surface described by the point cloud), which may be overlapping or not, such that each patch may be described by a depth field with respect to a plane in 2D space. In some embodiments, the patch generation module (306) aims at decomposing the point cloud into a minimum number of patches with smooth boundaries, while also minimizing the reconstruction error.

The patch info module (304) can collect the patch information that indicates sizes and shapes of the patches. In some examples, the patch information can be packed into an image frame and then encoded by the auxiliary patch info compression module (338) to generate the compressed auxiliary patch information.

The patch packing module (308) is configured to map the extracted patches onto a 2 dimensional (2D) grid while minimize the unused space and guarantee that every M×M (e.g., 16×16) block of the grid is associated with a unique patch. Efficient patch packing can directly impact the compression efficiency either by minimizing the unused space or ensuring temporal consistency.

The geometry image generation module (310) can generate 2D geometry images associated with geometry of the point cloud at given patch locations. The texture image generation module (312) can generate 2D texture images associated with texture of the point cloud at given patch locations. The geometry image generation module (310) and the texture image generation module (312) exploit the 3D to 2D mapping computed during the packing process to store the geometry and texture of the point cloud as images. In order to better handle the case of multiple points being projected to the same sample, each patch is projected onto two images, referred to as layers. In an example, geometry image is represented by a monochromatic frame of WxH in YUV420-8 bit format. To generate the texture image, the texture generation procedure exploits the reconstructed/smoothed geometry in order to compute the colors to be associated with the re-sampled points.

The occupancy map module (314) can generate an occupancy map that describes padding information at each unit. For example, the occupancy image includes a binary map that indicates for each cell of the grid whether the cell belongs to the empty space or to the point cloud. In an example, the occupancy map uses binary information describing for each pixel whether the pixel is padded or not. In another example, the occupancy map uses binary information describing for each block of pixels whether the block of pixels is padded or not.

The occupancy map generated by the occupancy map module (314) can be compressed using lossless coding or lossy coding. When lossless coding is used, the entropy compression module (334) is used to compress the occupancy map. When lossy coding is used, the video compression module (332) is used to compress the occupancy map.

It is noted that the patch packing module (308) may leave some empty spaces between 2D patches packed in an image frame. The image padding modules (316) and (318) can fill the empty spaces (referred to as padding) in order to generate an image frame that may be suited for 2D video and image codecs. The image padding is also referred to as background filling which can fill the unused space with redundant information. In some examples, a good background filling minimally increases the bit rate while does not introduce significant coding distortion around the patch boundaries.

The video compression modules (322), (323), and (332) can encode the 2D images, such as the padded geometry images, padded texture images, and occupancy maps based on a suitable video coding standard, such as HEVC, VVC and the like. In an example, the video compression modules (322), (323), and (332) are individual components that operate separately. It is noted that the video compression modules (322), (323), and (332) can be implemented as a single component in another example.

In some examples, the smoothing module (336) is configured to generate a smoothed image of the reconstructed geometry image. The smoothed image can be provided to the texture image generation (312). Then, the texture image generation (312) may adjust the generation of the texture image based on the reconstructed geometry images. For example, when a patch shape (e.g. geometry) is slightly distorted during encoding and decoding, the distortion may be taken into account when generating the texture images to correct for the distortion in patch shape.

In some embodiments, the group dilation (320) is configured to pad pixels around the object boundaries with redundant low-frequency content in order to improve coding gain as well as visual quality of reconstructed point cloud.

The multiplexer (324) can multiplex the compressed geometry image, the compressed texture image, the compressed occupancy map, the compressed auxiliary patch information into a compressed bitstream.

FIG. 4 shows a block diagram of a V-PCC decoder (400) for decoding compressed bitstream corresponding to point cloud frames, according to some embodiments. In some embodiments, the V-PCC decoder (400) can be used in the communication system (100) and streaming system (200). For example, the decoder (210) can be configured to operate in a similar manner as the V-PCC decoder (400). The V-PCC decoder (400) receives the compressed bitstream, and generates reconstructed point cloud based on the compressed bitstream.

In the FIG. 4 example, the V-PCC decoder (400) includes a de-multiplexer (432), video decompression modules (434) and (436), an occupancy map decompression module (438), an auxiliary patch-information decompression module (442), a geometry reconstruction module (444), a smoothing module (446), a texture reconstruction module (448), and a color smoothing module (452).

The de-multiplexer (432) can receive and separate the compressed bitstream into compressed texture image, compressed geometry image, compressed occupancy map, and compressed auxiliary patch information.

The video decompression modules (434) and (436) can decode the compressed images according to a suitable standard (e.g., HEVC, VVC, etc.) and output decompressed images. For example, the video decompression module (434) decodes the compressed texture images and outputs decompressed texture images; and the video decompression module (436) decodes the compressed geometry images and outputs the decompressed geometry images.

The occupancy map decompression module (438) can decode the compressed occupancy maps according to a suitable standard (e.g., HEVC, VVC, etc.) and output decompressed occupancy maps.

The auxiliary patch-information decompression module (442) can decode the compressed auxiliary patch information according to a suitable standard (e.g., HEVC, VVC, etc.) and output decompressed auxiliary patch information.

The geometry reconstruction module (444) can receive the decompressed geometry images, and generate reconstructed point cloud geometry based on the decompressed occupancy map and decompressed auxiliary patch information.

The smoothing module (446) can smooth incongruences at edges of patches. The smoothing procedure aims at alleviating potential discontinuities that may arise at the patch boundaries due to compression artifacts. In some embodiments, a smoothing filter may be applied to the pixels located on the patch boundaries to alleviate the distortions that may be caused by the compression/decompression.

The texture reconstruction module (448) can determine texture information for points in the point cloud based on the decompressed texture images and the smoothing geometry.

The color smoothing module (452) can smooth incongruences of coloring. Non-neighboring patches in 3D space are often packed next to each other in 2D videos. In some examples, pixel values from non-neighboring patches might be mixed up by the block-based video codec. The goal of color smoothing is to reduce the visible artifacts that appear at patch boundaries.

FIG. 5 shows a block diagram of a video decoder (510) according to an embodiment of the present disclosure. The video decoder (510) can be used in the V-PCC decoder (400). For example, the video decompression modules (434) and (436), the occupancy map decompression module (438) can be similarly configured as the video decoder (510).

The video decoder (510) may include a parser (520) to reconstruct symbols (521) from compressed images, such as the coded video sequence. Categories of those symbols include information used to manage operation of the video decoder (510). The parser (520) may parse/entropy-decode the coded video sequence that is received. The coding of the coded video sequence can be in accordance with a video coding technology or standard, and can follow various principles, including variable length coding, Huffman coding, arithmetic coding with or without context sensitivity, and so forth. The parser (520) may extract from the coded video sequence, a set of subgroup parameters for at least one of the subgroups of pixels in the video decoder, based upon at least one parameter corresponding to the group. Subgroups can include Groups of Pictures (GOPs), pictures, tiles, slices, macroblocks, Coding Units (CUs), blocks, Transform Units (TUs), Prediction Units (PUs) and so forth. The parser (520) may also extract from the coded video sequence information such as transform coefficients, quantizer parameter values, motion vectors, and so forth.

The parser (520) may perform an entropy decoding/parsing operation on the video sequence received from a buffer memory, so as to create symbols (521).

Reconstruction of the symbols (521) can involve multiple different units depending on the type of the coded video picture or parts thereof (such as: inter and intra picture, inter and intra block), and other factors. Which units are involved, and how, can be controlled by the subgroup control information that was parsed from the coded video sequence by the parser (520). The flow of such subgroup control information between the parser (520) and the multiple units below is not depicted for clarity.

Beyond the functional blocks already mentioned, the video decoder (510) can be conceptually subdivided into a number of functional units as described below. In a practical implementation operating under commercial constraints, many of these units interact closely with each other and can, at least partly, be integrated into each other. However, for the purpose of describing the disclosed subject matter, the conceptual subdivision into the functional units below is appropriate.

A first unit is the scaler/inverse transform unit (551). The scaler/inverse transform unit (551) receives a quantized transform coefficient as well as control information, including which transform to use, block size, quantization factor, quantization scaling matrices, etc. as symbol(s) (521) from the parser (520). The scaler/inverse transform unit (551) can output blocks comprising sample values that can be input into aggregator (555).

In some cases, the output samples of the scaler/inverse transform (551) can pertain to an intra coded block; that is: a block that is not using predictive information from previously reconstructed pictures, but can use predictive information from previously reconstructed parts of the current picture. Such predictive information can be provided by an intra picture prediction unit (552). In some cases, the intra picture prediction unit (552) generates a block of the same size and shape of the block under reconstruction, using surrounding already reconstructed information fetched from the current picture buffer (558). The current picture buffer (558) buffers, for example, partly reconstructed current picture and/or fully reconstructed current picture. The aggregator (555), in some cases, adds, on a per sample basis, the prediction information the intra prediction unit (552) has generated to the output sample information as provided by the scaler/inverse transform unit (551).

In other cases, the output samples of the scaler/inverse transform unit (551) can pertain to an inter coded, and potentially motion compensated block. In such a case, a motion compensation prediction unit (553) can access reference picture memory (557) to fetch samples used for prediction. After motion compensating the fetched samples in accordance with the symbols (521) pertaining to the block, these samples can be added by the aggregator (555) to the output of the scaler/inverse transform unit (551) (in this case called the residual samples or residual signal) so as to generate output sample information. The addresses within the reference picture memory (557) from where the motion compensation prediction unit (553) fetches prediction samples can be controlled by motion vectors, available to the motion compensation prediction unit (553) in the form of symbols (521) that can have, for example X, Y, and reference picture components. Motion compensation also can include interpolation of sample values as fetched from the reference picture memory (557) when sub-sample exact motion vectors are in use, motion vector prediction mechanisms, and so forth.

The output samples of the aggregator (555) can be subject to various loop filtering techniques in the loop filter unit (556). Video compression technologies can include in-loop filter technologies that are controlled by parameters included in the coded video sequence (also referred to as coded video bitstream) and made available to the loop filter unit (556) as symbols (521) from the parser (520), but can also be responsive to meta-information obtained during the decoding of previous (in decoding order) parts of the coded picture or coded video sequence, as well as responsive to previously reconstructed and loop-filtered sample values.

The output of the loop filter unit (556) can be a sample stream that can be output to a render device as well as stored in the reference picture memory (557) for use in future inter-picture prediction.

Certain coded pictures, once fully reconstructed, can be used as reference pictures for future prediction. For example, once a coded picture corresponding to a current picture is fully reconstructed and the coded picture has been identified as a reference picture (by, for example, the parser (520)), the current picture buffer (558) can become a part of the reference picture memory (557), and a fresh current picture buffer can be reallocated before commencing the reconstruction of the following coded picture.

The video decoder (510) may perform decoding operations according to a predetermined video compression technology in a standard, such as ITU-T Rec. H.265. The coded video sequence may conform to a syntax specified by the video compression technology or standard being used, in the sense that the coded video sequence adheres to both the syntax of the video compression technology or standard and the profiles as documented in the video compression technology or standard. Specifically, a profile can select certain tools as the only tools available for use under that profile from all the tools available in the video compression technology or standard. Also necessary for compliance can be that the complexity of the coded video sequence is within bounds as defined by the level of the video compression technology or standard. In some cases, levels restrict the maximum picture size, maximum frame rate, maximum reconstruction sample rate (measured in, for example megasamples per second), maximum reference picture size, and so on. Limits set by levels can, in some cases, be further restricted through Hypothetical Reference Decoder (HRD) specifications and metadata for HRD buffer management signaled in the coded video sequence.

FIG. 6 shows a block diagram of a video encoder (603) according to an embodiment of the present disclosure. The video encoder (603) can be used in the V-PCC encoder (300) that compresses point clouds. In an example, the video compression module (322) and (323), and the video compression module (332) are configured similarly to the encoder (603).

The video encoder (603) may receive images, such as padded geometry images, padded texture images and the like, and generate compressed images.

According to an embodiment, the video encoder (603) may code and compress the pictures of the source video sequence (images) into a coded video sequence (compressed images) in real time or under any other time constraints as required by the application. Enforcing appropriate coding speed is one function of a controller (650). In some embodiments, the controller (650) controls other functional units as described below and is functionally coupled to the other functional units. The coupling is not depicted for clarity. Parameters set by the controller (650) can include rate control related parameters (picture skip, quantizer, lambda value of rate-distortion optimization techniques, . . . ), picture size, group of pictures (GOP) layout, maximum motion vector search range, and so forth. The controller (650) can be configured to have other suitable functions that pertain to the video encoder (603) optimized for a certain system design.

In some embodiments, the video encoder (603) is configured to operate in a coding loop. As an oversimplified description, in an example, the coding loop can include a source coder (630) (e.g., responsible for creating symbols, such as a symbol stream, based on an input picture to be coded, and a reference picture(s)), and a (local) decoder (633) embedded in the video encoder (603). The decoder (633) reconstructs the symbols to create the sample data in a similar manner as a (remote) decoder also would create (as any compression between symbols and coded video bitstream is lossless in the video compression technologies considered in the disclosed subject matter). The reconstructed sample stream (sample data) is input to the reference picture memory (634). As the decoding of a symbol stream leads to bit-exact results independent of decoder location (local or remote), the content in the reference picture memory (634) is also bit exact between the local encoder and remote encoder. In other words, the prediction part of an encoder “sees” as reference picture samples exactly the same sample values as a decoder would “see” when using prediction during decoding. This fundamental principle of reference picture synchronicity (and resulting drift, if synchronicity cannot be maintained, for example because of channel errors) is used in some related arts as well.

The operation of the “local” decoder (633) can be the same as of a “remote” decoder, such as the video decoder (510), which has already been described in detail above in conjunction with FIG. 5. Briefly referring also to FIG. 5, however, as symbols are available and encoding/decoding of symbols to a coded video sequence by an entropy coder (645) and the parser (520) can be lossless, the entropy decoding parts of the video decoder (510), including and parser (520) may not be fully implemented in the local decoder (633).

An observation that can be made at this point is that any decoder technology except the parsing/entropy decoding that is present in a decoder also necessarily needs to be present, in substantially identical functional form, in a corresponding encoder. For this reason, the disclosed subject matter focuses on decoder operation. The description of encoder technologies can be abbreviated as they are the inverse of the comprehensively described decoder technologies. Only in certain areas a more detail description is required and provided below.

During operation, in some examples, the source coder (630) may perform motion compensated predictive coding, which codes an input picture predictively with reference to one or more previously-coded picture from the video sequence that were designated as “reference pictures”. In this manner, the coding engine (632) codes differences between pixel blocks of an input picture and pixel blocks of reference picture(s) that may be selected as prediction reference(s) to the input picture.

The local video decoder (633) may decode coded video data of pictures that may be designated as reference pictures, based on symbols created by the source coder (630). Operations of the coding engine (632) may advantageously be lossy processes. When the coded video data may be decoded at a video decoder (not shown in FIG. 6), the reconstructed video sequence typically may be a replica of the source video sequence with some errors. The local video decoder (633) replicates decoding processes that may be performed by the video decoder on reference pictures and may cause reconstructed reference pictures to be stored in the reference picture cache (634). In this manner, the video encoder (603) may store copies of reconstructed reference pictures locally that have common content as the reconstructed reference pictures that will be obtained by a far-end video decoder (absent transmission errors).

The predictor (635) may perform prediction searches for the coding engine (632). That is, for a new picture to be coded, the predictor (635) may search the reference picture memory (634) for sample data (as candidate reference pixel blocks) or certain metadata such as reference picture motion vectors, block shapes, and so on, that may serve as an appropriate prediction reference for the new pictures. The predictor (635) may operate on a sample block-by-pixel block basis to find appropriate prediction references. In some cases, as determined by search results obtained by the predictor (635), an input picture may have prediction references drawn from multiple reference pictures stored in the reference picture memory (634).

The controller (650) may manage coding operations of the source coder (630), including, for example, setting of parameters and subgroup parameters used for encoding the video data.

Output of all aforementioned functional units may be subjected to entropy coding in the entropy coder (645). The entropy coder (645) translates the symbols as generated by the various functional units into a coded video sequence, by lossless compressing the symbols according to technologies such as Huffman coding, variable length coding, arithmetic coding, and so forth.

The controller (650) may manage operation of the video encoder (603). During coding, the controller (650) may assign to each coded picture a certain coded picture type, which may affect the coding techniques that may be applied to the respective picture. For example, pictures often may be assigned as one of the following picture types:

An Intra Picture (I picture) may be one that may be coded and decoded without using any other picture in the sequence as a source of prediction. Some video codecs allow for different types of intra pictures, including, for example Independent Decoder Refresh (“IDR”) Pictures. A person skilled in the art is aware of those variants of I pictures and their respective applications and features.

A predictive picture (P picture) may be one that may be coded and decoded using intra prediction or inter prediction using at most one motion vector and reference index to predict the sample values of each block.

A bi-directionally predictive picture (B Picture) may be one that may be coded and decoded using intra prediction or inter prediction using at most two motion vectors and reference indices to predict the sample values of each block. Similarly, multiple-predictive pictures can use more than two reference pictures and associated metadata for the reconstruction of a single block.

Source pictures commonly may be subdivided spatially into a plurality of sample blocks (for example, blocks of 4×4, 8×8, 4×8, or 16×16 samples each) and coded on a block-by-block basis. Blocks may be coded predictively with reference to other (already coded) blocks as determined by the coding assignment applied to the blocks' respective pictures. For example, blocks of I pictures may be coded non-predictively or they may be coded predictively with reference to already coded blocks of the same picture (spatial prediction or intra prediction). Pixel blocks of P pictures may be coded predictively, via spatial prediction or via temporal prediction with reference to one previously coded reference picture. Blocks of B pictures may be coded predictively, via spatial prediction or via temporal prediction with reference to one or two previously coded reference pictures.

The video encoder (603) may perform coding operations according to a predetermined video coding technology or standard, such as ITU-T Rec. H.265. In its operation, the video encoder (603) may perform various compression operations, including predictive coding operations that exploit temporal and spatial redundancies in the input video sequence. The coded video data, therefore, may conform to a syntax specified by the video coding technology or standard being used.

A video may be in the form of a plurality of source pictures (images) in a temporal sequence. Intra-picture prediction (often abbreviated to intra prediction) makes use of spatial correlation in a given picture, and inter-picture prediction makes uses of the (temporal or other) correlation between the pictures. In an example, a specific picture under encoding/decoding, which is referred to as a current picture, is partitioned into blocks. When a block in the current picture is similar to a reference block in a previously coded and still buffered reference picture in the video, the block in the current picture can be coded by a vector that is referred to as a motion vector. The motion vector points to the reference block in the reference picture, and can have a third dimension identifying the reference picture, in case multiple reference pictures are in use.

In some embodiments, a bi-prediction technique can be used in the inter-picture prediction. According to the bi-prediction technique, two reference pictures, such as a first reference picture and a second reference picture that are both prior in decoding order to the current picture in the video (but may be in the past and future, respectively, in display order) are used. A block in the current picture can be coded by a first motion vector that points to a first reference block in the first reference picture, and a second motion vector that points to a second reference block in the second reference picture. The block can be predicted by a combination of the first reference block and the second reference block.

Further, a merge mode technique can be used in the inter-picture prediction to improve coding efficiency.

According to some embodiments of the disclosure, predictions, such as inter-picture predictions and intra-picture predictions are performed in the unit of blocks. For example, according to the HEVC standard, a picture in a sequence of video pictures is partitioned into coding tree units (CTU) for compression, the CTUs in a picture have the same size, such as 64×64 pixels, 32×32 pixels, or 16×16 pixels. In general, a CTU includes three coding tree blocks (CTBs), which are one luma CTB and two chroma CTBs. Each CTU can be recursively quadtree split into one or multiple coding units (CUs). For example, a CTU of 64×64 pixels can be split into one CU of 64×64 pixels, or 4 CUs of 32×32 pixels, or 16 CUs of 16×16 pixels. In an example, each CU is analyzed to determine a prediction type for the CU, such as an inter prediction type or an intra prediction type. The CU is split into one or more prediction units (PUs) depending on the temporal and/or spatial predictability. Generally, each PU includes a luma prediction block (PB), and two chroma PBs. In an embodiment, a prediction operation in coding (encoding/decoding) is performed in the unit of a prediction block. Using a luma prediction block as an example of a prediction block, the prediction block includes a matrix of values (e.g., luma values) for pixels, such as 8×8 pixels, 16×16 pixels, 8×16 pixels, 16×8 pixels, and the like.

FIG. 7 shows a block diagram of a G-PPC encoder (700) in accordance with some embodiments. The encoder (700) can be configured to receive point cloud data and compress the point cloud data to generate a bit stream carrying compressed point cloud data. In an embodiment, the encoder (700) can include a position quantization module (710), a duplicated points removal module (712), an octree encoding module (730), an attribute transfer module (720), a level of detail (LOD) generation module (740), an attribute prediction module (750), a residual quantization module (760), an arithmetic coding module (770), an inverse residual quantization module (780), an addition module (781), and a memory (790) to store reconstructed attribute values.

As shown, an input point cloud (701) can be received at the encoder (700). Positions (e.g., 3D coordinates) of the point cloud (701) are provided to the quantization module (710). The quantization module (710) is configured to quantize the coordinates to generate quantized positions. The duplicated points removal module (712) is configured to receive the quantized positions and perform a filter process to identify and remove duplicated points. The octree encoding module (730) is configured to receive filtered positions from the duplicated points removal module (712), and perform an octree-based encoding process to generate a sequence of occupancy codes that describe a 3D grid of voxels. The occupancy codes are provided to the arithmetic coding module (770).

The attribute transfer module (720) is configured to receive attributes of the input point cloud, and perform an attribute transfer process to determine an attribute value for each voxel when multiple attribute values are associated with the respective voxel. The attribute transfer process can be performed on the re-ordered points output from the octree encoding module (730). The attributes after the transfer operations are provided to the attribute prediction module (750). The LOD generation module (740) is configured to operate on the re-ordered points output from the octree encoding module (730), and re-organize the points into different LODs. LOD information is supplied to the attribute prediction module (750).

The attribute prediction module (750) processes the points according to an LOD-based order indicated by the LOD information from the LOD generation module (740). The attribute prediction module (750) generates an attribute prediction for a current point based on reconstructed attributes of a set of neighboring points of the current point stored in the memory (790). Prediction residuals can subsequently be obtained based on original attribute values received from the attribute transfer module (720) and locally generated attribute predictions. When candidate indices are used in the respective attribute prediction process, an index corresponding to a selected prediction candidate may be provided to the arithmetic coding module (770).

The residual quantization module (760) is configured to receive the prediction residuals from the attribute prediction module (750), and perform quantization to generate quantized residuals. The quantized residuals are provided to the arithmetic coding module (770).

The inverse residual quantization module (780) is configured to receive the quantized residuals from the residual quantization module (760), and generate reconstructed prediction residuals by performing an inverse of the quantization operations performed at the residual quantization module (760). The addition module (781) is configured to receive the reconstructed prediction residuals from the inverse residual quantization module (780), and the respective attribute predictions from the attribute prediction module (750). By combining the reconstructed prediction residuals and the attribute predictions, the reconstructed attribute values are generated and stored to the memory (790).

The arithmetic coding module (770) is configured to receive the occupancy codes, the candidate indices (if used), the quantized residuals (if generated), and other information, and perform entropy encoding to further compress the received values or information. As a result, a compressed bitstream (702) carrying the compressed information can be generated. The bitstream (702) may be transmitted, or otherwise provided, to a decoder that decodes the compressed bitstream, or may be stored in a storage device.

FIG. 8 shows a block diagram of a G-PCC decoder (800) in accordance with an embodiment. The decoder (800) can be configured to receive a compressed bitstream and perform point cloud data decompression to decompress the bitstream to generate decoded point cloud data. In an embodiment, the decoder (800) can include an arithmetic decoding module (810), an inverse residual quantization module (820), an octree decoding module (830), an LOD generation module (840), an attribute prediction module (850), and a memory (860) to store reconstructed attribute values.

As shown, a compressed bitstream (801) can be received at the arithmetic decoding module (810). The arithmetic decoding module (810) is configured to decode the compressed bitstream (801) to obtain quantized residuals (if generated) and occupancy codes of a point cloud. The octree decoding module (830) is configured to determine reconstructed positions of points in the point cloud according to the occupancy codes. The LOD generation module (840) is configured to re-organize the points into different LODs based on the reconstructed positions, and determine an LOD-based order. The inverse residual quantization module (820) is configured to generate reconstructed residuals based on the quantized residuals received from the arithmetic decoding module (810).

The attribute prediction module (850) is configured to perform an attribute prediction process to determine attribute predictions for the points according to the LOD-based order. For example, an attribute prediction of a current point can be determined based on reconstructed attribute values of neighboring points of the current point stored in the memory (860). In some examples, the attribute prediction can be combined with a respective reconstructed residual to generate a reconstructed attribute for the current point.

A sequence of reconstructed attributes generated from the attribute prediction module (850) together with the reconstructed positions generated from the octree decoding module (830) corresponds to a decoded point cloud (802) that is output from the decoder (800) in one example. In addition, the reconstructed attributes are also stored into the memory (860) and can be subsequently used for deriving attribute predictions for subsequent points.

In various embodiments, the encoder (300), the decoder (400), the encoder (700), and/or the decoder (800) can be implemented with hardware, software, or combination thereof. For example, the encoder (300), the decoder (400), the encoder (700), and/or the decoder (800) can be implemented with processing circuitry such as one or more integrated circuits (ICs) that operate with or without software, such as an application specific integrated circuit (ASIC), field programmable gate array (FPGA), and the like. In another example, the encoder (300), the decoder (400), the encoder (700), and/or the decoder (800) can be implemented as software or firmware including instructions stored in a non-volatile (or non-transitory) computer-readable storage medium. The instructions, when executed by processing circuitry, such as one or more processors, causing the processing circuitry to perform functions of the encoder (300), the decoder (400), the encoder (700), and/or the decoder (800).

It is noted that the attribute prediction modules (750) and (850) configured to implement the attribute prediction techniques disclosed herein can be included in other decoders or encoders that may have similar or different structures from what is shown in FIG. 7 and FIG. 8. In addition, the encoder (700) and decoder (800) can be included in a same device, or separate devices in various examples.

Aspects of the disclosure provide techniques for use in G-PCC. Specifically, node-based geometry and/or attribute coding techniques for G-PCC are described in the following description.

According to some aspects of the disclosure, geometry information and the associated attributes of a point cloud, such as color, reflectance and the like can be separately compressed (e.g., in the MPEG G-PCC Test Model 13 (TMC13) model). The geometry information of the point cloud, which includes the 3D coordinates of the points in the point cloud, can be coded by partitions with occupancy information of the partitions, such as an octree partition, quadtree-partition and binary partition with occupancy information of the partitions. After the geometry information is coded, the attributes can be compressed based on a reconstructed geometry using, for example, prediction, lifting and region adaptive hierarchical transform techniques.

For geometry coding, several techniques can be used. The several techniques can include tree based geometry coding, predictive tree based geometry coding and trisoup based geometry coding. The tree based geometry coding, predictive tree based geometry coding and trisoup based geometry coding will be described respectively.

According to an aspect of the disclosure, a three dimensional space can be partitioned using tree partition, such as octree partition, quadtree partition, binary tree partition and the like. Using octree partition as an example, octrees are the three dimensional analog of quadtrees in the two dimensional space. Octree partition technique refers to the partition technique that recursively subdivides three dimensional space into eight octants, and an octree structure refers to the tree structure that represents the partitions. In an example, each node in the octree structure corresponds to a three dimensional space, and the node can be an end node (no more partition, also referred to as leaf node in some examples) or a node with a further partition. An octree partition at a node can partition the three dimensional space represented by the node into eight octants. In some examples, nodes corresponding to partitions of a specific node can be referred to as child nodes of the specific node.

FIG. 9 shows a diagram illustrating a partition of a 3D cube (900) (corresponding to a node) based on the octree partition technique according to some embodiments of the disclosure. The partition can divide the 3D cube (900) into eight smaller equal-sized cubes 0-7 as shown in FIG. 9. In the FIG. 9, the x, y and z dimensions of the 3D cube (900) are respectively divided into half and division can result 8 sub-cubes with the same size.

The octree partition technique (e.g., in TMC13) can recursively divide an original 3D space into the smaller units, and the occupancy information of every sub-space can be encoded to represent geometry positions.

In some embodiments (e.g., In TMC13), an octree geometry codec is used. The octree geometry codec can perform geometry encoding. In some examples, geometry encoding is performed on a cubical box. For example, the cubical box can be an axis-aligned bounding box B that is defined by two points (0,0,0) and (2^(M−1),2^(M−1),2^(M−1)), where 2^(M−1) defines the size of the bounding box B and M can be specified in the bitstream.

Then, an octree structure is built by recursively subdividing the cubical box. For example, the cubical box defined by the two points (0,0,0) and (2^(M−1),2^(M−1),2^(M−1)) is divided into 8 sub cubical boxes, then an 8-bit code, that is referred to as an occupancy code, is generated. Each bit of the occupancy code is associated with a sub cubical box, and the value of the bit is used to indicate whether the associated sub cubical box contains any points of the point cloud. For example, value 1 of a bit indicates that the sub cubical box associated with the bit contains one or more points of the point cloud; and value 0 of a bit indicates that the sub cubical box associated with the bit contains no point of the point cloud.

Further, for empty sub cubical box (e.g., the value of the bit associated with the sub cubical box is 0), no more division is applied on the sub cubical box. When a sub cubical box has one or more points of the point cloud (e.g., the value of the bit associated with the sub cubical box is 1), the sub cubical box is further divided into 8 smaller sub cubical boxes, and an occupancy code can be generated for the sub cubical box to indicate the occupancy of the smaller sub cubical boxes. In some examples, the subdivision operations can be repetitively performed on non-empty sub cubical boxes until the size of the sub cubical boxes is equal to a predetermined threshold, such as size being 1. In some examples, the sub cubical boxes with a size of 1 are referred to as voxels, and the sub cubical boxes that have larger sizes than voxels can be referred to as non-voxels.

FIG. 10 shows an example of an octree partition (1010) and an octree structure (1020) corresponding to the octree partition (1010) according to some embodiments of the disclosure. FIG. 10 shows two levels of partitions in the octree partition (1010). The octree structure (1020) includes a node (NO) corresponding to the cubical box for octree partition (1010). The node NO is at depth 0 of the octree structure (1020). At a first level of partition, the cubical box is partitioned into 8 sub cubical boxes that are numbered 0-7 according to the numbering technique shown in FIG. 9. The occupancy code for the partition of the node NO is “10000001” in binary, which indicates the first sub cubical box represented by node N0-0 and the eighth sub cubical box represented by node N0-7 includes points in the point cloud and other sub cubical boxes are empty. The nodes N0-0 to N0-7 are at depth 1 of the octree structure (1020).

Then, at the second level of partition, the first sub cubical box (represented by node N0-0) and the eighth sub cubical box (represented by node N0-7) are further respectively sub-divided into eight octants. For example, the first sub cubical box (represented by node N0-0) is partitioned into 8 smaller sub cubical boxes that are numbered 0-7 according to the numbering technique shown in FIG. 9. The occupancy code for the partition of the node N0-0 is “00011000” in binary, which indicates the fourth smaller sub cubical box (represented by node N0-0-3) and the fifth smaller sub cubical box (represented by node N0-0-4) includes points in the point cloud and other smaller sub cubical boxes are empty. The nodes N0-0-0 to N0-0-7 are at depth 2 of the octree structure (1020). At the second level, the eighth sub cubical box (represented by node N0-7) is similarly partitioned into 8 smaller sub cubical boxes as shown in FIG. 10. The nodes N0-7-0 to N0-7-7 are at depth 2 of the octree structure (1020).

In the FIG. 10 example, the nodes corresponding to non-empty cubical space (e.g., cubical box, sub cubical boxes, smaller sub cubical boxes and the like) are colored in grey, and referred to as shaded nodes. The nodes corresponding to empty cubical space (e.g., cubical box, sub cubical boxes, smaller sub cubical boxes and the like) are colored in white, and can be referred to as blank nodes.

While octree partition is described in the above description, generally tree based geometry coding technique can partition a point cloud using other partitions, such as quadtree or binary tree partitions.

More generally, for a point cloud, the bounding box B of the point cloud is not restricted to be with same size in all directions, instead the bounding box B can be arbitrary-size rectangular cuboid to better fit the shape of the 3D scene or objects. In some examples, the size of the bounding box B can be represented as a power of two, such as (2 ^(d) ^(x) ,2 ^(d) ^(y) ,2 ^(d) ^(z) ). In an example, d_(x),d_(y),d_(z) are not equal.

To partition a bounding box B of a point cloud, in addition to the octree partition in the above description, quadtree partition and binary tree partition in the following description can be used.

FIG. 11 shows three quadtree partitions in some examples. For a quadtree partition, two of three dimensions (e.g., x, y, and z dimensions) of a bounding box B can be splitting into half, and the quadtree partition can result 4 sub-boxes with the same size.

In the FIG. 11 example, a bounding box (1110) is split by quadtree partition in the x and y dimensions, the result of the quadtree partition is shown by 4 sub-boxes with the same size that are labeled as 0, 2, 4, and 6.

Further, in the FIG. 11 example, a bounding box (1120) is split by quadtree partition in the x and z dimensions, the result of the quadtree partition is shown by 4 sub-boxes with the same size that are labeled as 0, 1, 4, and 5.

Further, in the FIG. 11 example, a bounding box (1130) is split by quadtree partition in the y and z dimensions, the result of the quadtree partition is shown by 4 sub-boxes with the same size that are labeled as 0, 1, 2, and 3.

FIG. 12 shows three binary tree partitions in some examples. For a binary tree partition, one of three dimensions (e.g., x, y, and z dimensions) of a bounding box B can be splitting into half, and the binary tree partition can result 2 sub-boxes with the same size.

In the FIG. 12 example, a bounding box (1210) is split by binary tree partition in the x dimension, the result of the binary partition is shown by 2 sub-boxes with the same size that are labeled as 0, and 4.

Further, in the FIG. 12 example, a bounding box (1220) is split by binary tree partition in the y dimension, the result of the binary partition is shown by 2 sub-boxes with the same size that are labeled as 0, and 2.

Further, in the FIG. 12 example, a bounding box (1230) is split by binary tree partition in the z dimension, the result of the binary partition is shown by 2 sub-boxes with the same size that are labeled as 0, and 1.

Accordingly, a point cloud can be represented by a general tree structure with a suitable mix of octree partition, quadtree partition and binary tree partition. To traverse a tree structure, in some examples (e.g., a version of TMC13 model), a breadth-first approach is adopted. In some other examples, a depth-first approach can also be used.

In some related examples, (e.g., a version of TMC13), to code the occupancy codes, the tree structure is traversed in the breadth first order. According to the breadth first order, tree nodes (e.g., nodes in the tree structure) in a level can be visited after all of the tree nodes in an upper level have been visited. In an implementation example, a first-in-first-out (FIFO) data structure can be used.

FIG. 13 shows a diagram of an octree structure (1300) illustrating breadth first coding order. The shaded nodes in the octree structure (1300) are nodes corresponding to cubical spaces that are not empty and are occupied by one or more points in the point cloud. The occupancy codes for the shaded nodes can be coded in the breadth first coding order from 0 to 8 shown in FIG. 13. In the breadth first coding order, the octree nodes are visited level-by-level. According to an aspect of the disclosure, the breadth first coding order by itself is not suitable for parallel processing because the current level has to wait for the upper level to be coded.

In some examples, a hybrid coding order that includes at least one level that is coded using a depth first coding order instead of the breadth first coding order. Thus, in some embodiments, a node at the level with the depth first coding order and descendant nodes of the node can form a sub tree structure of the tree structure. When the level with depth first coding order includes multiple nodes respectively corresponding to non-empty cubical spaces, the multiple nodes and their corresponding descendant nodes can form multiple sub tree structures. The multiple sub tree structures can be coded in parallel in some embodiments.

FIG. 14 shows a diagram of an octree structure (1400) illustrating depth first coding order. The shaded nodes in the octree structure (1400) are nodes corresponding to cubical spaces that are not empty. The octree structure (1400) can correspond to same occupancy geometry of a point cloud as the octree structure (1300). The occupancy codes for the shaded nodes can be coded in the depth first coding order from 0 to 8 shown in FIG. 14.

In the FIG. 14 example, node “0” can be at any suitable partition depth, such as PD0, child nodes of the node “0” are at the partition depth PD0+1, and grandchild nodes of the node “0” are at the partition depth PD0+2. In the FIG. 14 example, nodes at partition depth PD0+1 can be coded in a depth first coding order. The nodes at the partition depth PD0+1 include two nodes that correspond to non-empty space. The two nodes and their respectively descendant nodes can form a first sub octree structure (1410) and a second sub octree structure (1420), the two nodes can be respectively referred to as root nodes of the two sub octree structures.

The depth first coding order in FIG. 14 is referred to as a preorder version of the depth first coding order. In the preorder version of the depth first coding order, for each sub octree structure, the root node of the sub octree is visited first before visiting the child nodes of the sub octree structure. Further, the deepest node is first visited and then track back to the siblings of the parent node.

In the FIG. 14 example, the first sub octree structure (1410) and the second sub octree structure (1420) can be coded in parallel processing in some implementations. For example, node 1 and node 5 can be visited at the same time. In some examples, recursion programming or stack data structure can be used to implement the depth first coding order.

In some embodiments, the hybrid coding order starts with the breadth first traversing (coding), and after several levels of breadth first traversing, the depth-first traversing (coding) can be enabled.

In some examples, predictive tree based geometry coding can be used. Predictive tree based geometry coding can be used when a predictive tree, such as a spanning tree can be constructed over all the points in the point cloud. In an example, for a prediction of a point, all ancestors can be used.

FIG. 15 shows a portion of a predictive tree (1510) that spans a point cloud (1500) of a rabbit. In some examples, the position of a point in the predictive tree (1510) can be predicted from the position of its parent point, or from the positions of its parent and its grandparent point.

In some examples, trisoup based geometry coding can be used. The trisoup based geometry coding approach can represent surfaces of an object as a series of triangle mesh. In an example, the trisoup based geometry coding approach is applied for a dense surface point cloud. A decoder using the trisoup based geometry coding can generate a point cloud from the mesh surface in the specified voxel granularity to assure the density of the reconstructed point cloud. According to an aspect of the disclosure, trisoup based geometry coding can introduce distortion to the original point cloud, but may provide the benefit of reduced bitstream size.

For attribute coding, several techniques can be used. The techniques include prediction based attribute coding, lifting based attribute coding, region adaptive hierarchical transform (RAHT) based attribute coding and the like. The prediction based attribute coding, lifting based attribute coding, and RAHT based attribute coding and the like will be respectively described in the following description.

For prediction based attribute coding, let (P_(i))_(i=l) _(N) denote a set of positions associated with points in a point cloud. For each position that is represented by a multi dimensional data, a Morton code of one dimension can be determined to be associated with the position. Let (M_(i))_(i=l) _(N) denote the Morton codes respectively associated with positions (P_(i))_(i=l) _(N) . The prediction based attribute coding includes a sorting step followed by a coding step. In the sorting step, the points in the point cloud are sorted according to the associated Morton codes in for example an ascending order. For example, let I denote an array of indexes for the points that are ordered according to the sorting step.

In the coding step, the encoder/decoder can compress/decompress respectively the points according to the order defined by I in iterations. At each iteration i, a point P_(i) is selected following the order defined by I. The distances of P_(i) to a number of previous points in the order analyzed. For example, s (e.g., s=64) denotes the number of previous points that are analyzed. Based on the analyzed, k (e.g., k=3) nearest neighbors of P_(i) are selected to be used for attribute prediction. Specifically, in some examples, an attribute (α_(i)) of a point i can be predicted by using a linear interpolation process of attributes of k nearest neighbors (α_(h))_(h∈∪) _(k-1) that are weighted based on the distances of the nearest neighbours to the point i. In an example, at a decoder side, let

denote the set of the k-nearest neighbours of the current point i, let

denote decoded/reconstructed attribute values of the neighbours and let (δ_(t))_(t∈)

_(i) denote their distances to the current point i. Then, the predicted attribute value {circumflex over (α)}₁ for the current point i can be calculated based on attribute values of the neighbors and their distances to the current point according to Eq. (1):

$\begin{matrix} {â_{i} = {{Round}\left( {\sum_{j \in}{\aleph_{i}\frac{\frac{1}{\delta_{j}^{2}}}{{\Sigma t} \in {\aleph_{i}\frac{1}{\delta_{j}^{2}}}}{\overset{\sim}{a}}_{j}}} \right)}} & {{Eq}.(1)} \end{matrix}$

For lifting based attribute coding, additional steps are applied upon the prediction-based coding. In an example, two additional steps that are referred to as a first step of an update operator and a second step of an adaptive quantization are used.

FIG. 16 shows a diagram of using a direct/forward transform architecture (1600) in the lifting based attribute coding at an encoder side of G-PCC. In some examples, to facilitate prediction and update, the direct/forward transform architecture (1600) includes multiple prediction/update (P/U) decompose stages to decompose an attribute signal. At each of the multiple P/U decompose stages, a signal (approximation signal) from previous stage is split into two sets of high-correlation. In an example, in the lifting based attribute coding scheme of G-PCC, the splitting is performed by leveraging level of details (LoD) structure in which such high-correlation is expected among levels and each level is constructed by a nearest neighbor search to organize non-uniform point clouds into a structured data. A P/U decomposition stage at a stage (N) results in a detail signal D(N) and an approximation signal L′(N), which is further decomposed into D(N−1) and L′(N−1) in a next stage (e.g., stage (N−1)). The decomposition is repeatedly applied until a base layer approximation signal L′(0) is obtained in an example. Consequently, instead of coding an input attribute signal itself that consists of various levels of details, detail signals D(N), D(N−1), . . . , D(0), and the base layer approximation signal L′(0) can be coded in the lifting based attribute coding scheme.

It is noted that the application of P/U decomposition stages can result in sparse sub-bands in the coefficients in D(N), . . . , D(0), thereby providing a transform coding gain advantage.

FIG. 17 shows a diagram of using an inverse transform architecture (1700) in the lifting based attribute coding at a decoder side of G-PCC. The inverse transform architecture (1700) includes multiple prediction/update (P/U) merge stages to reconstruct an attribute signal. At each P/U merge stage, a detail signal is decoded and merged with an approximation signal from a previous stage to generate a new approximation signal for providing to the next P/U merge stage.

For RAHT based attribute coding, adaptive hierarchical transform can be used.

FIG. 18 shows a diagram of a RAHT forward transform architecture (1810) that can be used in an encoder side of G-PCC and a diagram of a RAHT inverse transform architecture (1820) that can be used in a decoder side of G-PCC. In the FIG. 18 example,

${a^{2} = {{\frac{w_{0}}{w_{0} + w_{1}}{and}b^{2}} = \frac{w_{1}}{w_{0} + w_{1}}}},$

and w₀ is the notation of the weight of the input coefficient F_(l+1,2n) while w₁ is the same for F_(l+l,2n+1).

According to some aspects of the disclosure, geometry and attribute coding for a point cloud can be performed in the manner of a node-based geometry and attribute coding. In tree-based geometry coding, a point cloud is represented as a general tree structure, for example, using octree partition, quad-tree and binary tree partitions. The root node of the tree structure corresponds to the whole volume of the point cloud while the intermediate nodes of the tree structure correspond to sub-volumes of the point cloud (or sub-trees of the tree structure).

Referring back to FIG. 10, the octree structure (1020) is used as an example of a tree structure. For convenience, the node N0 is a root node and at depth 0 of the tree structure. A partition at a node can result nodes with larger depth (e.g., depth increases by one). For example, a partition of a box corresponding to the node N0 can result nodes at depth 1 of the tree structure. A partition of a sub-box at depth (k−1) can result nodes at depth k of the tree structure. Partitions can be performed until all the nodes are unit nodes, for example, size in all three dimensions is 1 in some examples.

In some embodiments, instead of coding attributes after the geometry coding of the whole point cloud is completed, attributes can be coded in between geometry coding of the point cloud. In some examples, the geometry of a point cloud can be coded until depth k is reached, where k is a positive integer and can be specified by an encoder and transmitted in the coded bitstream. In a first example, the geometry coding and attribute coding can be performed in a sub-volume based interleave manner at depth k. Specifically, for example, for each occupied node at depth k, which corresponds to a sub-volume (or subtree) of the point cloud, the geometry information of points in the sub-volume (or nodes in the subtree) can be encoded first, and attribute information of the points in the sub-volume (or the nodes in the subtree) can be encoded following the geometry information of the points (or the nodes in the subtree). Then, the encoding process can go to a next occupied node at depth k. Thus, attribute information of a first occupied node at depth k (e.g., attribute information of points in a first sub volume corresponding to the first occupied node) is encoded before geometry information of a second occupied node at depth k (e.g., geometry information of points in a second sub volume corresponding to the second occupied node) in the coded bitstream.

In a second example, the geometry coding and attribute coding can be performed in a node based interleaved manner from depth k. For example, for each node at depth k and depth deeper than k, the geometry information of the node can be encoded first, and attribute information of the node can be encoded following the geometry information of the node. Then, the encoding process can go to a next node a depth k or depth deeper than k. Thus, attribute information of a first node is encoded before geometry information of a second node in the coded bitstream.

In the first example of the sub-volume based interleave manner at depth k and the second example of the node based interleaved manner, the nodes at depth k can be treated as the top-level coding unit, in a similar manner as the largest coding unit (LCU) used in HEVC video coding standard. In some examples, in the field of the point cloud coding, each node at depth k form a separate subtree and each subtree can be referred to as an LCU in point cloud coding. The point cloud can be coded using LCU based coding. The LCU based coding can be referred to as node based coding in some examples. The LCU based coding can include LCU based geometry coding, and LCU based geometry and attribute coding. The LCU based geometry coding can code geometry information based on LCUs. The LCU based geometry and attribute coding can code geometry information and attribute information based on LCUs, such as in the sub-volume based interleave manner, in the node based interleave manner, and the like.

FIG. 19 shows a tree structure (1900) corresponding to a point cloud according to some examples of the disclosure. In FIG. 19, the nodes corresponding to non-empty space are colored in grey, and referred to as shaded nodes. The nodes corresponding to empty space are colored in white, and can be referred to as blank nodes. The shaded nodes are numbered according to a coding sequence.

In the FIG. 19 example, the nodes at depth 1 are LCUs. For example, the tree structure (1900) includes a first LCU (1910) and a second LCU (1920). The point cloud can be coded using node-based geometry and attribute coding (also referred to as LCU based geometry and attribute coding). In some examples of node-based geometry and attribute coding in the sub-volume based interleave manner at depth 1, the geometry information of nodes in the first LCU (1910) is coded and attribute information of the nodes in the first LCU (1910) is coded after the geometry information of the nodes in the first LCU (1910). Then, the geometry information of nodes in the second LCU (1920) is coded after the attribute information of the nodes in the first LCU (1910), and attribute information of the nodes in the second LCU (1920) is coded after the geometry information of the nodes in the second LCU (1920). For simplicity, a node at depth k (k=1 in FIG. 19) can be referred to as an LCU in the present disclosure. In the present disclosure, LCU and a node at depth k can be interchangeable.

In some examples, node-based geometry and attribute coding is performed in the node based interleave manner. For example, the geometry information of node 1 is coded and then attribute information of the node 1 is coded after the geometry information of the node 1. Then, the geometry information of node 2 is coded after the attribute information of the node 1, and attribute information of the node 2 is coded after the geometry information of the node 2.

For simplicity, quadtree partitions are used in the tree structure (1900) for illustration. It is noted that other partitions, such as octree partitions, binary tree partitions can be used in a tree structure.

According to an aspect of the disclosure, on the encoder side, the generated bitstreams for both geometry and attributes of each node (e.g., LCU) can be transmitted without waiting for the completion of the geometry coding of the whole point cloud. On the decoder side, a decoder can decode the points in a corresponding node (e.g., LCU) and display them without waiting for the completion of the decoding of the geometry of the whole point cloud. Thus, low latency encoding and decoding can be achieved by using node based geometry and attribute coding.

It is noted that occupied nodes at depth k (e.g., LCUs) can be coded in any suitable order. In an example, the occupied nodes at depth k (e.g., LCUs) are coded in Morton order. In another example, the occupied nodes at depth k are coded in other space-filling order, other than Morton code.

In some examples, coding of geometry and attribute of an LCU doesn't depend on information of its neighboring LCU(s). Specifically, predictions/references across LCU boundaries are disabled, and the context and history information are reinitialized for each LCU as well. The history information can include geometry occupancy information of nodes with depth smaller than k. Thus, LCUs can be encoded or decoded independently (referred to as LCU coding independence). The LCU coding independence can enable maximum parallelism at depth k, i.e., LCU level parallel encoding and decoding.

In some other examples, coding of geometry and attribute of an LCU can rely on information of its neighbors (e.g., neighboring LCUs). For example, coding of geometry and attribute of an LCU relies on information of its already coded neighboring nodes and their coded child nodes (referred to as LCU coding dependence). The LCU coding dependence can help to gain better compression efficiency.

In some embodiments, parallel node based (LCU based) coding techniques can be used in point cloud coding. To achieve parallel node based (LCU-based) coding, coding of geometry and attribute of an LCU cannot depend on information of its neighboring LCUs. To achieve parallel processing and avoid uncertainty, predictions/references across LCU boundaries are disabled and coding state information, such as the context information and history information need to be reinitialized to a known coding state consistent at the encoder and the decoder side, for each LCU as well.

In an embodiment, at each LCU, the coding state, such as the context for entropy coding, geometry occupancy history information, and other necessary state information of LCU based coding, can be set to an initial state, which is the coding state when coding of the point cloud starts.

In another embodiment, instead of using the initial state, a suitable intermediate coding state, such as a coding state (including context for entropy coding and geometry occupancy history information, and other necessary state information of LCU based coding), right before the first LCU is reached (e.g., after the coding of tree depth (k−1) is completed) can be stored. The nodes at tree depth k can be coded according to LCU based coding. When encoding each LCU, the coding state can be set based on the stored intermediate coding state. Then, parallel node-based (LCU-base) coding can be achieved. In addition, the stored intermediate coding state may help improve the coding performance, compared to the initial coding state when the coding process starts.

FIG. 20 shows a flow chart outlining a coding process (2000) for coding geometry information and/or attribute information according to some embodiments of the disclosure.

At (S2010), coding of depth (k−1) of a tree structure is completed before the coding of any occupied nodes at depth k. The occupied nodes at depth k of the tree structure are referred as LCU nodes, and the LCU nodes respectively correspond to subtrees in the tree structure, and can be coded by LCU based coding (e.g., LCU based geometry coding, LCU based geometry and attribute coding). In some examples, the LCU nodes can be coded in parallel.

At (S2020), a variable N is set to be the number of LCUs at depth k (e.g., occupied nodes at the depth k) of the tree structure and a variable I is initialized, for example to 0. The variable I is used to track the index of the LCUs.

At (S2030), the variable I is compared with the variable N. When the variable I is smaller than variable N, the process proceeds to (S2040); otherwise, coding of the LCUs are completed, and the process can proceed to further coding process.

At (S2040), when the variable I is equal to 0, the corresponding LCU with the index having the value of the variable I is the first LCU, then the process proceeds to (S2050); otherwise, the process proceeds to (S2060).

At (S2050), the coding state (including context for entropy coding and geometry occupancy history information, and other necessary state information of LCU based coding) is stored.

At (S2060), the coding state is restored from the stored coding state.

At (S2070), the LCU with index having the value of the variable I is coded using LCU based coding.

At (S2080), the variable I increases by one, and the process returns to (S2030).

It is noted that the process (2000) can be suitably modified.

FIG. 21 shows a flow chart outlining another coding process (2100) for coding geometry information and/or attribute information according to some embodiments of the disclosure.

At (S2110), coding of depth (k−1) of a tree structure is completed before the coding of occupied nodes at depth k. The occupied nodes at depth k of the tree structure are referred as LCU nodes, and the LCU nodes respectively correspond to subtrees in the tree structure, and can be coded by LCU based coding (e.g., LCU based geometry coding, LCU based geometry and attribute coding). In some examples, the LCU nodes can be coded in parallel.

At (S2120), a variable N is set to be the number of LCUs at depth k (e.g., number of occupied nodes at depth k) of the tree structure and a variable I is initialized, for example to 0. The variable I is used to track the index of the LCUs.

At (S2130), the coding state (including context for entropy coding and geometry occupancy history information, and other necessary state information of LCU based coding) is stored.

At (S2140), the variable I is compared with the variable N. When the variable I is smaller than variable N, the process proceeds to (S2150); otherwise, coding of the LCUs are completed, and the process can proceed to further coding process.

At (S2150), the coding state is restored from the stored coding state.

At (S2160), the LCU with index having the value of the variable I is coded using LCU based geometry and attribute coding.

At (S2170), the variable I increases by one, and the process returns to (S2140).

According to some aspects of the disclosure, a flag is used to provide additional information to control the storage and restore of the coding state information for the LCU based coding. The techniques disclosed in the present disclosure can be applied in any suitable software, standard or system for PCC.

In the implementation of parallel node-based (LCU-based) coding, the coding state can be saved right before the first LCU is reached. When coding each LCU, the saved coding state can be restored. Thus, thus coding state for LCUs can be known and consistent at the encoder side and decoder side. In this way, parallel node-based (LCU-base) coding can be achieved. In some examples, parallel coding is not needed, for the purpose of reducing memory and operations, the coding state information does not have to be saved and restored.

According to an aspect of the disclosure, a flag can be used to control whether to save and restore the coding state. In some examples, the flag can be added in the high-level syntax, for example, in the sequence parameter set, geometry parameter set or slice header to control whether to save and restore the coding state. The flag can be referred to as state store flag.

FIG. 22A shows a syntax table in a geometry header (2200A) according to some embodiments of the disclosure. The geometry header (2200A) includes a geometry parameter set that can be transmitted in the coded bitstream that carries the point cloud from the encoder side to the decoder side. The geometry parameter set includes a flag (2210), for example with a name “gps_save_state_flag”, to control whether to save and restore the coding state. Specifically, in some examples, in response to the flag “gps_save_state_flag” having a binary value “1”, coding state information before the first LCU is stored, and before coding each LCU (or each subsequent LCU), coding state can be restored according to the stored coding state information. On the other hand, in response to the flag “gps_save_state_flag” having a binary value “0”, no coding state storing and restoring operations are performed.

In some examples, LCU coding only includes geometry coding, the state store flag is included in the geometry header, such as the geometry header (2200A).

In some examples, LCU coding includes both geometry coding and attribute coding, and the state store flag is included in sequence parameter set to control the LCU coding of both geometry and attribute coding.

FIG. 22B shows a syntax table in a sequence header (2200B) according to some embodiments of the disclosure. The sequence header (2200B) includes a sequence parameter set that can be transmitted in the coded bitstream that carries the point cloud from the encoder side to the decoder side. The sequence parameter set includes a flag (2220), for example with a name “save_state_flag”, to control whether to save and restore the coding state. Specifically, in some examples, in response to the flag “save_state_flag” having a binary value “1”, coding state information before the first LCU is stored, and before coding each LCU (or each subsequent LCU), coding state can be restored according to the stored coding state information. On the other hand, in response to the flag “save_state_flag” having a binary value “0”, no coding state storing and restoring operations are performed.

FIG. 23 shows a flow chart outlining a coding process (2300) for coding geometry information and/or attribute information according to some embodiments of the disclosure.

At (S2310), coding of depth (k−1) of a tree structure is completed before the coding of any occupied nodes at depth k. The occupied nodes at depth k of the tree structure are referred as LCU nodes, and the LCU nodes respectively correspond to subtrees in the tree structure, and can be coded by LCU based coding (e.g., LCU based geometry coding, LCU based geometry and attribute coding). In some examples, the LCUs can be coded in parallel. In some examples, the LCUs are coded one by one, not by parallel processing.

At (S2320), a variable N is set to be the number of LCUs at depth k (e.g., occupied nodes at the depth k) of the tree structure and a variable I is initialized, for example to 0. The variable I is used to track the index of the LCUs.

At (S2330), the variable I is compared with the variable N. When the variable I is smaller than variable N, the process proceeds to (S2340); otherwise, coding of the LCUs are completed, and the process can proceed to further coding process.

At (S2340), when the variable I is equal to 0, the corresponding LCU with the index having the value of the variable I is the first LCU, then the process proceeds to (S2350); otherwise, the process proceeds to (S2360).

At (S2350), if a flag that is referred to as state store flag, such as the flag “gps_save_state_flag” in the case of LCU based geometry coding, or the flag “save_state_flag” in the case of LCU based geometry and attribute coding, is equal to binary value “1”, the process proceeds to (S2355) for storing coding state; otherwise, the process proceeds to (S2370) without storing the coding state.

At (S2355), the coding state (including context for entropy coding and geometry occupancy history information, and other necessary state information of LCU based coding) is stored.

At (S2360), if the state store flag, such as the flag “gps_save_state_flag” in the case of LCU based geometry coding, or the flag “save_state_flag” in the case of LCU based geometry and attribute coding, is equal to binary value “1”, the process proceeds to (S2365) for restoring the coding state; otherwise, the process proceeds to (S2370) without restoring the coding state.

At (S2365) the coding state is restored from the stored coding state.

At (S2370), the LCU with index having the value of the variable I is coded using LCU based coding.

At (S2380), the variable I increases by one, and the process returns to (S2330).

It is noted that, in some examples, when the state store flag (e.g., the flag “gps_save_state_flag” in the case of LCU based geometry coding, or the flag “save_state_flag” in the case of LCU based geometry and attribute coding) has the binary value “1”, the LCUs are coded in parallel; and when the state store flag (e.g., the flag “gps_save_state_flag” in the case of LCU based geometry coding, or the flag “save_state_flag” in the case of LCU based geometry and attribute coding) has the binary value “0”, LCUs are coded one by one, not by parallel processing.

It is noted that the process (2300) can be suitably modified.

FIG. 24 shows a flow chart outlining another coding process (2400) for coding geometry information and/or attribute information according to some embodiments of the disclosure.

At (S2410), coding of depth (k−1) of a tree structure is completed before the coding of occupied nodes at depth k. The occupied nodes at depth k of the tree structure are referred as LCU nodes, and the LCU nodes respectively correspond to subtrees in the tree structure, and can be coded by LCU based coding (e.g., LCU based geometry coding, LCU based geometry and attribute coding). In some examples, the LCUs can be coded in parallel. In some examples, the LCUs are coded one by one, not by parallel processing.

At (S2420), a variable N is set to be the number of LCUs at depth k (e.g., number of occupied nodes at depth k) of the tree structure and a variable I is initialized, for example to 0. The variable I is used to track the index of the LCUs.

At (S2430), the coding state (including context for entropy coding and geometry occupancy history information, and other necessary state information of LCU based coding) is stored. It is noted that in some examples, the coding state is stored when a flag that is referred to as a state store flag (e.g., the flag “gps_save_state_flag” in the case of LCU based geometry coding, or the flag “save_state_flag” in the case of LCU based geometry and attribute coding) is equal to binary value “1”.

At (S2440), the variable I is compared with the variable N. When the variable I is smaller than variable N, the process proceeds to (S2445); otherwise, coding of the LCUs are completed, and the process can proceed to further coding process.

At (S2445), if a flag that is referred to as a state store flag (e.g., the flag “gps_save_state_flag” in the case of LCU based geometry coding, or the flag “save_state_flag” in the case of LCU based geometry and attribute coding) is equal to binary value “1”, the process proceeds to (S2450) for restoring the coding state; otherwise, the process proceeds to (S2460) without restoring the coding state.

At (S2450), the coding state is restored from the stored coding state.

At (S2460), the LCU with index having the value of the variable I is coded using LCU based geometry coding or LCU based geometry and attribute coding.

At (S2470), the variable I increases by one, and the process returns to (S2440).

FIG. 25 shows a flow chart outlining a process (2500) according to an embodiment of the disclosure. The process (2500) can be used during a decoding process for a point cloud. In various embodiments, the process (2500) is executed by processing circuitry, such as the processing circuitry in the terminal devices (110), the processing circuitry that performs functions of the encoder (203) and/or the decoder (210), the encoder (700), and/or the decoder (800), and the like. In some embodiments, the process (2500) is implemented in software instructions, thus when the processing circuitry executes the software instructions, the processing circuitry performs the process (2500). The process starts at (S2501) and proceeds to (S2510).

At (S2510), a flag that indicates an enable/disable control for saving coding state in a largest coding unit (LCU) based coding of a point cloud is determined. In some embodiments, the flag is decoded from at least one of a sequence parameter set in a sequence header, a geometry parameter set in a geometry header, and a slice header.

At (S2520), coding state information before a coding of a first LCU is stored. In an example, the coding state information is stored in in response to the flag indicating an enable control. In another example, the storing of the coding state information is skipped in response to the flag indicating the disable control for saving coding state. In an example, the coding state information is stored regardless of the flag.

In some examples, the coding state information includes at least one of context information, history geometry occupancy information and other suitable history information.

At (S2530), in response to the flag indicating the enable control, a coding state before a coding of a second LCU is restored according to the stored coding state information. In some examples, the restoring of the coding state according to the stored coding state information before the coding of the second LCU can be skipped in response to the flag indicating a disable control for saving coding state.

In some embodiments, the flag is decoded from a geometry parameter set in a geometry header, such as the flag “gps_save_state_flag”. Then, the coding state information is stored before a geometry coding of the first LCU; and the coding state is restored before a geometry coding of the second LCU according to the stored coding state information.

In some embodiments, the flag is decoded from a sequence parameter set in a sequence header, such as the flag “save_state_flag”. Then, the coding state information is stored before a geometry and attribute coding of the first LCU; and the coding state is restored, before a geometry and attribute coding of the second LCU, according to the stored coding state information.

In some embodiments, the LCUs can be coded in parallel. For example, the coding of the second LCU can start without a completion of the coding of the first LCU.

Then, the process proceeds to (S2599) and terminates.

The techniques disclosed in the present disclosure may be used separately or combined in any order. Further, each of the techniques (e.g., methods, embodiments), encoder, and decoder may be implemented by processing circuitry (e.g., one or more processors or one or more integrated circuits). In some examples, the one or more processors execute a program that is stored in a non-transitory computer-readable medium.

The techniques described above, can be implemented as computer software using computer-readable instructions and physically stored in one or more computer-readable media. For example, FIG. 26 shows a computer system (2600) suitable for implementing certain embodiments of the disclosed subject matter.

The computer software can be coded using any suitable machine code or computer language, that may be subject to assembly, compilation, linking, or like mechanisms to create code comprising instructions that can be executed directly, or through interpretation, micro-code execution, and the like, by one or more computer central processing units (CPUs), Graphics Processing Units (GPUs), and the like.

The instructions can be executed on various types of computers or components thereof, including, for example, personal computers, tablet computers, servers, smartphones, gaming devices, internet of things devices, and the like.

The components shown in FIG. 26 for computer system (2600) are exemplary in nature and are not intended to suggest any limitation as to the scope of use or functionality of the computer software implementing embodiments of the present disclosure. Neither should the configuration of components be interpreted as having any dependency or requirement relating to any one or combination of components illustrated in the exemplary embodiment of a computer system (2600).

Computer system (2600) may include certain human interface input devices. Such a human interface input device may be responsive to input by one or more human users through, for example, tactile input (such as: keystrokes, swipes, data glove movements), audio input (such as: voice, clapping), visual input (such as: gestures), olfactory input (not depicted). The human interface devices can also be used to capture certain media not necessarily directly related to conscious input by a human, such as audio (such as: speech, music, ambient sound), images (such as: scanned images, photographic images obtain from a still image camera), video (such as two-dimensional video, three-dimensional video including stereoscopic video).

Input human interface devices may include one or more of (only one of each depicted): keyboard (2601), mouse (2602), trackpad (2603), touch screen (2610), data-glove (not shown), joystick (2605), microphone (2606), scanner (2607), camera (2608).

Computer system (2600) may also include certain human interface output devices. Such human interface output devices may be stimulating the senses of one or more human users through, for example, tactile output, sound, light, and smell/taste. Such human interface output devices may include tactile output devices (for example tactile feedback by the touch-screen (2610), data-glove (not shown), or joystick (2605), but there can also be tactile feedback devices that do not serve as input devices), audio output devices (such as: speakers (2609), headphones (not depicted)), visual output devices (such as screens (2610) to include CRT screens, LCD screens, plasma screens, OLED screens, each with or without touch-screen input capability, each with or without tactile feedback capability—some of which may be capable to output two dimensional visual output or more than three dimensional output through means such as stereographic output; virtual-reality glasses (not depicted), holographic displays and smoke tanks (not depicted)), and printers (not depicted).

Computer system (2600) can also include human accessible storage devices and their associated media such as optical media including CD/DVD ROM/RW (2620) with CD/DVD or the like media (2621), thumb-drive (2622), removable hard drive or solid state drive (2623), legacy magnetic media such as tape and floppy disc (not depicted), specialized ROM/ASIC/PLD based devices such as security dongles (not depicted), and the like.

Those skilled in the art should also understand that term “computer readable media” as used in connection with the presently disclosed subject matter does not encompass transmission media, carrier waves, or other transitory signals.

Computer system (2600) can also include an interface (2654) to one or more communication networks (2655). Networks can for example be wireless, wireline, optical. Networks can further be local, wide-area, metropolitan, vehicular and industrial, real-time, delay-tolerant, and so on. Examples of networks include local area networks such as Ethernet, wireless LANs, cellular networks to include GSM, 3G, 4G, 5G, LTE and the like, TV wireline or wireless wide area digital networks to include cable TV, satellite TV, and terrestrial broadcast TV, vehicular and industrial to include CANBus, and so forth. Certain networks commonly require external network interface adapters that attached to certain general purpose data ports or peripheral buses (2649) (such as, for example USB ports of the computer system (2600)); others are commonly integrated into the core of the computer system (2600) by attachment to a system bus as described below (for example Ethernet interface into a PC computer system or cellular network interface into a smartphone computer system). Using any of these networks, computer system (2600) can communicate with other entities. Such communication can be uni-directional, receive only (for example, broadcast TV), uni-directional send-only (for example CANbus to certain CANbus devices), or bi-directional, for example to other computer systems using local or wide area digital networks. Certain protocols and protocol stacks can be used on each of those networks and network interfaces as described above.

Aforementioned human interface devices, human-accessible storage devices, and network interfaces can be attached to a core (2640) of the computer system (2600).

The core (2640) can include one or more Central Processing Units (CPU) (2641), Graphics Processing Units (GPU) (2642), specialized programmable processing units in the form of Field Programmable Gate Areas (FPGA) (2643), hardware accelerators for certain tasks (2644), graphics adapters (2650), and so forth. These devices, along with Read-only memory (ROM) (2645), Random-access memory (2646), internal mass storage such as internal non-user accessible hard drives, SSDs, and the like (2647), may be connected through a system bus (2648). In some computer systems, the system bus (2648) can be accessible in the form of one or more physical plugs to enable extensions by additional CPUs, GPU, and the like. The peripheral devices can be attached either directly to the core's system bus (2648), or through a peripheral bus (2649). In an example, the screen (2610) can be connected to the graphics adapter (2650). Architectures for a peripheral bus include PCI, USB, and the like.

CPUs (2641), GPUs (2642), FPGAs (2643), and accelerators (2644) can execute certain instructions that, in combination, can make up the aforementioned computer code. That computer code can be stored in ROM (2645) or RAM (2646). Transitional data can be also be stored in RAM (2646), whereas permanent data can be stored for example, in the internal mass storage (2647). Fast storage and retrieve to any of the memory devices can be enabled through the use of cache memory, that can be closely associated with one or more CPU (2641), GPU (2642), mass storage (2647), ROM (2645), RAM (2646), and the like.

The computer readable media can have computer code thereon for performing various computer-implemented operations. The media and computer code can be those specially designed and constructed for the purposes of the present disclosure, or they can be of the kind well known and available to those having skill in the computer software arts.

As an example and not by way of limitation, the computer system having architecture (2600), and specifically the core (2640) can provide functionality as a result of processor(s) (including CPUs, GPUs, FPGA, accelerators, and the like) executing software embodied in one or more tangible, computer-readable media. Such computer-readable media can be media associated with user-accessible mass storage as introduced above, as well as certain storage of the core (2640) that are of non-transitory nature, such as core-internal mass storage (2647) or ROM (2645). The software implementing various embodiments of the present disclosure can be stored in such devices and executed by core (2640). A computer-readable medium can include one or more memory devices or chips, according to particular needs. The software can cause the core (2640) and specifically the processors therein (including CPU, GPU, FPGA, and the like) to execute particular processes or particular parts of particular processes described herein, including defining data structures stored in RAM (2646) and modifying such data structures according to the processes defined by the software. In addition or as an alternative, the computer system can provide functionality as a result of logic hardwired or otherwise embodied in a circuit (for example: accelerator (2644)), which can operate in place of or together with software to execute particular processes or particular parts of particular processes described herein. Reference to software can encompass logic, and vice versa, where appropriate. Reference to a computer-readable media can encompass a circuit (such as an integrated circuit (IC)) storing software for execution, a circuit embodying logic for execution, or both, where appropriate. The present disclosure encompasses any suitable combination of hardware and software.

While this disclosure has described several exemplary embodiments, there are alterations, permutations, and various substitute equivalents, which fall within the scope of the disclosure. It will thus be appreciated that those skilled in the art will be able to devise numerous systems and methods which, although not explicitly shown or described herein, embody the principles of the disclosure and are thus within the spirit and scope thereof. 

What is claimed is:
 1. A method for point cloud coding, comprising: determining, by a processor, a flag that indicates an enable/disable control for saving coding state in a largest coding unit (LCU) based coding of a point cloud; storing, by the processor, coding state information before a coding of a first LCU; and restoring, by the processor and in response to the flag indicating an enable control, a coding state according to the stored coding state information before a coding of a second LCU.
 2. The method of claim 1, further comprising: storing, in response to the flag indicating the enable control, the coding state information before the coding of the first LCU.
 3. The method of claim 2, further comprising: skipping, in response to the flag indicating a disable control, the storing of the coding state information.
 4. The method of claim 1, further comprising: skipping, in response to the flag indicating a disable control, the restoring of the coding state.
 5. The method of claim 1, further comprising: decoding the flag from at least one of a sequence parameter set in a sequence header, a geometry parameter set in a geometry header, and a slice header.
 6. The method of claim 1, further comprising: decoding the flag from a geometry parameter set in a geometry header; storing the coding state information before a geometry coding of the first LCU; and restoring the coding state according to the stored coding state information before a geometry coding of the second LCU.
 7. The method of claim 1, further comprising: decoding the flag from a sequence parameter set in a sequence header; storing the coding state information before a geometry and attribute coding of the first LCU; and restoring the coding state according to the stored coding state information before a geometry and attribute coding of the second LCU.
 8. The method of claim 1, further comprising: coding the second LCU without a completion of the coding of the first LCU.
 9. The method of claim 1, further comprising: skipping the restoring of the coding state according to the stored coding state information before the coding of the second LCU in response to the flag indicating a disable control for saving coding state.
 10. The method of claim 9, further comprising: skipping the storing of the coding state information in response to the flag indicating the disable control for saving coding state.
 11. The method of claim 1, wherein the coding state information includes at least one of context information and history geometry occupancy information.
 12. An apparatus for point cloud coding, comprising processing circuitry configured to: determine a flag that indicates an enable/disable control for saving coding state in a largest coding unit (LCU) based coding of a point cloud; store coding state information before a coding of a first LCU; and restore, in response to the flag indicating an enable control, a coding state according to the stored coding state information before a coding of a second LCU.
 13. The apparatus of claim 12, wherein the processing circuitry is configured to: store, in response to the flag indicating the enable control, the coding state information before the coding of the first LCU.
 14. The apparatus of claim 13, wherein the processing circuitry is configured to: skip, in response to the flag indicating a disable control, the storing of the coding state information.
 15. The apparatus of claim 12, wherein the processing circuitry is configured to: skip, in response to the flag indicating a disable control, the restoring of the coding state.
 16. The apparatus of claim 12, wherein the processing circuitry is configured to: decode the flag from at least one of a sequence parameter set in a sequence header, a geometry parameter set in a geometry header, and a slice header.
 17. The apparatus of claim 12, wherein the processing circuitry is configured to: decode the flag from a geometry parameter set in a geometry header; store, the coding state information before a geometry coding of the first LCU; and restore, the coding state according to the stored coding state information before a geometry coding of the second LCU.
 18. The apparatus of claim 12, wherein the processing circuitry is configured to: decode the flag from a sequence parameter set in a sequence header; store, the coding state information before a geometry and attribute coding of the first LCU; and restore, the coding state according to the stored coding state information before a geometry and attribute coding of the second LCU.
 19. The apparatus of claim 12, wherein the processing circuitry is configured to: code the second LCU without a completion of the coding of the first LCU.
 20. The apparatus of claim 12, wherein the processing circuitry is configured to: skip the restoring of the coding state according to the stored coding state information before the coding of the second LCU in response to the flag indicating a disable control for saving coding state. 